Facilitation of deep service path discovery for 5g or other next generation network

ABSTRACT

A software defined network (SDN) can add network repository functions (NRF) into a configurations database to enable NF discovery. The SDN can subscribe to NRF notifications to receive new cloud native functions (CNF), registrations, or any other update to the CNF status in 5G system. In addition to listening to NRF notifications, the SDN can implement CNF pooling processes to periodically retrieve CNF from an NRF repository and stay in sync with 5G systems. Thus, a deep service path discovery can be developed from network service configurations and container call flows to enable an accurate alarm correlation and troubleshooting for the operations. This service path deep discovery can be designed and implemented as a standalone system or in an SDN framework with integration of a container management framework such as K8 kubernetes.

TECHNICAL FIELD

This disclosure relates generally to facilitating deep service pathdiscovery. For example, this disclosure relates to facilitating deepservice path discovery for cloud native functions for a 5G, or othernext generation network, air interface.

BACKGROUND

5^(th) generation (5G) wireless systems represent a next major phase ofmobile telecommunications standards beyond the currenttelecommunications standards of 4^(th) generation (4G). 5G can supporthigher capacity than current 4G, allowing a higher number of mobilebroadband users per area unit, and allowing consumption of higher dataquantities. This would enable a large portion of the population tostream high-definition media many hours per day with their mobiledevices, when out of reach of wireless fidelity hotspots. 5G networksalso provide improved support of machine-to-machine communication, alsoknown as the Internet of things, enabling lower cost, lower batteryconsumption, and lower latency than 4G equipment.

The above-described background is merely intended to provide acontextual overview of some current issues, and is not intended to beexhaustive. Other contextual information may become further apparentupon review of the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the subject disclosureare described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 illustrates an example wireless communication system in which anetwork node device (e.g., network node) and user equipment (UE) canimplement various aspects and embodiments of the subject disclosure.

FIG. 2 illustrates an example schematic system block diagram of a masternode according to one or more embodiments.

FIG. 3 illustrates an example schematic system block diagram of acontainerized network function architecture according to one or moreembodiments.

FIG. 4 illustrates an example schematic system block diagram of a deepservice path discovery architecture according to one or moreembodiments.

FIG. 5 illustrates an example schematic system block diagram of cloudnative function deep service path discovery architecture according toone or more embodiments.

FIG.6 illustrates an example flow diagram for a method for deep servicepath discovery according to one or more embodiments.

FIG. 7 illustrates an example flow diagram for a system for deep servicepath discovery according to one or more embodiments.

FIG. 8 illustrates an example flow diagram for a machine-readable mediumdeep service path discovery according to one or more embodiments.

FIG. 9 illustrates an example block diagram of an example mobile handsetoperable to engage in a system architecture that facilitates securewireless communication according to one or more embodiments describedherein.

FIG. 10 illustrates an example block diagram of an example computeroperable to engage in a system architecture that facilitates securewireless communication according to one or more embodiments describedherein.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth toprovide a thorough understanding of various embodiments. One skilled inthe relevant art will recognize, however, that the techniques describedherein can be practiced without one or more of the specific details, orwith other methods, components, materials, etc. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring certain aspects.

Reference throughout this specification to “one embodiment,” or “anembodiment,” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearances of the phrase “in oneembodiment,” “in one aspect,” or “in an embodiment,” in various placesthroughout this specification are not necessarily all referring to thesame embodiment. Furthermore, the particular features, structures, orcharacteristics may be combined in any suitable manner in one or moreembodiments.

As utilized herein, terms “component,” “system,” “interface,” and thelike are intended to refer to a computer-related entity, hardware,software (e.g., in execution), and/or firmware. For example, a componentcan be a processor, a process running on a processor, an object, anexecutable, a program, a storage device, and/or a computer. By way ofillustration, an application running on a server and the server can be acomponent. One or more components can reside within a process, and acomponent can be localized on one computer and/or distributed betweentwo or more computers.

Further, these components can execute from various machine-readablemedia having various data structures stored thereon. The components cancommunicate via local and/or remote processes such as in accordance witha signal having one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network, e.g., the Internet, a local areanetwork, a wide area network, etc. with other systems via the signal).

As another example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry; the electric or electronic circuitry can beoperated by a software application or a firmware application executed byone or more processors; the one or more processors can be internal orexternal to the apparatus and can execute at least a part of thesoftware or firmware application. As yet another example, a componentcan be an apparatus that provides specific functionality throughelectronic components without mechanical parts; the electroniccomponents can include one or more processors therein to executesoftware and/or firmware that confer(s), at least in part, thefunctionality of the electronic components. In an aspect, a componentcan emulate an electronic component via a virtual machine, e.g., withina cloud computing system.

The words “exemplary” and/or “demonstrative” are used herein to meanserving as an example, instance, or illustration. For the avoidance ofdoubt, the subject matter disclosed herein is not limited by suchexamples. In addition, any aspect or design described herein as“exemplary” and/or “demonstrative” is not necessarily to be construed aspreferred or advantageous over other aspects or designs, nor is it meantto preclude equivalent exemplary structures and techniques known tothose of ordinary skill in the art. Furthermore, to the extent that theterms “includes,” “has,” “contains,” and other similar words are used ineither the detailed description or the claims, such terms are intendedto be inclusive - in a manner similar to the term “comprising” as anopen transition word - without precluding any additional or otherelements.

As used herein, the term “infer” or “inference” refers generally to theprocess of reasoning about, or inferring states of, the system,environment, user, and/or intent from a set of observations as capturedvia events and/or data. Captured data and events can include user data,device data, environment data, data from sensors, sensor data,application data, implicit data, explicit data, etc. Inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events, for example.

Inference can also refer to techniques employed for composinghigher-level events from a set of events and/or data. Such inferenceresults in the construction of new events or actions from a set ofobserved events and/or stored event data, whether the events arecorrelated in close temporal proximity, and whether the events and datacome from one or several event and data sources. Various classificationschemes and/or systems (e.g., support vector machines, neural networks,expert systems, Bayesian belief networks, fuzzy logic, and data fusionengines) can be employed in connection with performing automatic and/orinferred action in connection with the disclosed subject matter.

In addition, the disclosed subject matter can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, machine-readable device, computer-readablecarrier, computer-readable media, or machine-readable media.

As an overview, various embodiments are described herein to facilitatedeep service path discovery for cloud native functions for a 5G airinterface or other next generation networks. For simplicity ofexplanation, the methods are depicted and described as a series of acts.It is to be understood and appreciated that the various embodiments arenot limited by the acts illustrated and/or by the order of acts. Forexample, acts can occur in various orders and/or concurrently, and withother acts not presented or described herein. Furthermore, not allillustrated acts may be desired to implement the methods. In addition,the methods could alternatively be represented as a series ofinterrelated states via a state diagram or events. Additionally, themethods described hereafter are capable of being stored on an article ofmanufacture (e.g., a machine-readable medium) to facilitate transportingand transferring such methodologies to computers. The term article ofmanufacture, as used herein, is intended to encompass a computer programaccessible from any computer-readable device, carrier, or media,including a non-transitory machine-readable medium.

It should be noted that although various aspects and embodiments havebeen described herein in the context of 5G, or other next generationnetworks, the disclosed aspects are not limited to 5G, a universalmobile telecommunications system (UMTS) implementation, a long termevolution (LTE) implementation, and/or other network implementations, asthe techniques can also be applied in 3G, or 4G systems. For example,aspects or features of the disclosed embodiments can be exploited insubstantially any wireless communication technology. Such wirelesscommunication technologies can include UMTS, global system for mobilecommunication (GSM), code division multiple access (CDMA), wideband CDMA(WCMDA), CDMA2000, time division multiple access (TDMA), frequencydivision multiple access (FDMA), multi-carrier CDMA (MC-CDMA),single-carrier CDMA (SC-CDMA), single-carrier FDMA (SC-FDMA), orthogonalfrequency division multiplexing (OFDM), discrete Fourier transformspread OFDM (DFT-spread OFDM), single carrier FDMA (SC-FDMA), filterbank based multi-carrier (FBMC), zero tail DFT-spread-OFDM (ZTDFT-s-OFDM), generalized frequency division multiplexing (GFDM), fixedmobile convergence (FMC), universal fixed mobile convergence (UFMC),unique word OFDM (UW-OFDM), unique word DFT-spread OFDM (UWDFT-Spread-OFDM), cyclic prefix OFDM (CP-OFDM), resource-block-filteredOFDM, wireless fidelity (Wi-Fi), worldwide interoperability formicrowave access (WiMAX), wireless local area network (WLAN), generalpacket radio service (GPRS), enhanced GPRS, third generation partnershipproject (3GPP), LTE, LTE frequency division duplex (FDD), time divisionduplex (TDD), 5G, third generation partnership project 2 (3GPP2), ultramobile broadband (UMB), high speed packet access (HSPA), evolved highspeed packet access (HSPA+), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Zigbee, or another institute ofelectrical and electronics engineers (IEEE) 802.12 technology. In thisregard, all or substantially all aspects disclosed herein can beexploited in legacy telecommunication technologies.

Described herein are systems, methods, articles of manufacture, andother embodiments or implementations that can facilitate deep servicepath discovery for cloud native functions for a 5G network. Facilitatingdeep service path discovery for cloud native functions for a 5G networkcan be implemented in connection with any type of device with aconnection to the communications network (e.g., a mobile handset, acomputer, a handheld device, etc.) any Internet of things (TOT) device(e.g., toaster, coffee maker, blinds, music players, speakers, etc.),and/or any connected vehicles (cars, airplanes, space rockets, and/orother at least partially automated vehicles (e.g., drones)). In someembodiments, the non-limiting term user equipment (UE) is used. It canrefer to any type of wireless device that communicates with a radionetwork node in a cellular or mobile communication system. Examples of aUE are a target device, a device to device (D2D) UE, a machine type UE,a UE capable of machine to machine (M2M) communication, personal digitalassistant (PDA), a Tablet or tablet computer, a mobile terminal, a smartphone, an IOT device, a laptop or laptop computer, a laptop havinglaptop embedded equipment (LEE, such as a mobile broadband adapter),laptop mounted equipment (LME), a universal serial bus (USB) dongleenabled for mobile communications, a computer having mobilecapabilities, a mobile broadband adapter, a wearable device, a virtualreality (VR) device, a heads-up display (HUD) device, a smart vehicle(e.g., smart car), a machine-type communication (MTC) device, etc. A UEcan have one or more antenna panels having vertical and horizontalelements. The embodiments are applicable to single carrier, multicarrier(MC), or carrier aggregation (CA) operation(s) of the UE. The termcarrier aggregation (CA) is also referred to in connection with (e.g.,interchangeably referenced as) a “multi-carrier system”, a “multi-celloperation”, a “multi-carrier operation”, “multi-carrier” transmissionand/or “multi-carrier” reception.

In some embodiments, the non-limiting term radio network node, or simplynetwork node, is used. It can refer to any type of network node thatserves a UE or network equipment connected to other network nodes,network elements, or any radio node from where a UE receives a signal.Non-exhaustive examples of radio network nodes are Node B, base station(BS), multi-standard radio (MSR) node such as MSR BS, eNode B, gNode B,network controller, radio network controller (RNC), base stationcontroller (BSC), relay, donor node controlling relay, base transceiverstation (BTS), edge nodes, edge servers, network access equipment,network access nodes, a connection point to a telecommunicationsnetwork, such as an access point (AP), transmission points, transmissionnodes, remote radio unit (RRU), remote radio head (RRH), nodes indistributed antenna system (DAS), etc.

Cloud radio access networks (RAN) can enable the implementation ofconcepts such as software-defined network (SDN) and network functionvirtualization (NFV) in 5G networks. This disclosure can facilitate ageneric channel state information framework design for a 5G network.Certain embodiments of this disclosure can include an SDN controllerthat can control routing of traffic within the network and between thenetwork and traffic destinations. The SDN controller can be merged withthe 5G network architecture to enable service deliveries via openapplication programming interfaces (“APIs”) and move the network coretowards an all internet protocol (“IP”), cloud based, and softwaredriven telecommunications network. The SDN controller can work with, ortake the place of policy and charging rules function (“PCRF”) networkelements so that policies such as quality of service and trafficmanagement and routing can be synchronized and managed end to end.

5G, also called new radio (NR) access, networks can support thefollowing: data rates of several tens of megabits per second supportedfor tens of thousands of users; 1 gigabit per second offeredsimultaneously or concurrently to tens of workers on the same officefloor; several hundreds of thousands of simultaneous or concurrentconnections for massive sensor deployments; enhanced spectral efficiencycompared to 4G or LTE; improved coverage compared to 4G or LTE; enhancedsignaling efficiency compared to 4G or LTE; and reduced latency comparedto 4G or LTE. In multicarrier systems, such as OFDM, each subcarrier canoccupy bandwidth (e.g., subcarrier spacing). If carriers use the samebandwidth spacing, then the bandwidth spacing can be considered a singlenumerology. However, if the carriers occupy different bandwidth and/orspacing, then the bandwidth spacing can be considered a multiplenumerology.

The 5G network functions can be managed by kubernetes to provide anetwork service. However, the containers that perform network trafficprocessing are transient. The current model relies on staticinformation, but the containers are transient objects within thekubernetes infrastructure. A network repository function (NRF) has theability to communicate through application program interfaces (API) witha set of network functions (NFs) (e.g., access and mobility managementfunction (AMF), session management function (SMF), and/or user planefunction (UPF)). If other NFs want to forward a specific packat throughthe network, then the AMF can determine the SMF such that the other NFscan register with the SMF to forward a call.

A cloud native function (CNF) architecture can create new challenges formobile network operators (MNO) when it comes to having visibility intothe network call flow and service paths for troubleshooting while theCNF inter-ops with a virtual networking function (vNF) or a physicalnetworking function (pNF). For troubleshooting, alarm correlation,and/or performance management of service paths, a logical view of theservice path connection and the traffic can flow from a radio accessnetwork (RAN) into a core containerized network function residing in thecloud infrastructure. The current model of the PNF/CNF, inventory andthe service path end point are not sufficient for 5G systems withcontainerized network functions because the selection of the servicepaths in a container can be dynamic by a K8 kubernetes proxy in the CNFarchitecture. Introducing a network service slice with a containerizedsolution can increase the magnitude of this problem as the networkbecomes a logical slice that is applicable to a cloud nativecontainerized network function.

A network repository function (NRF) implementation can comply withoperations, administrations, and management (OAM) APIs for notificationsand info for 5G system network functions. K8 APIs can provide CNFservice APIs and other log info for a call flow that is supported by aCNF. A cloud service provider can provide cloud fabric configurations.An SDN can add the NRF into a configurations database to enablediscovery of NFs. The SDN can then subscribe to the NRF notifications toreceive new CNF registrations and/or any other updates to the CNFstatus. The K8 can instantiate a CNF with a container image and otherconfiguration metadata to enable the CNF for services. In addition tolistening to NRF notifications, the SDN can implement a poolingalgorithm to periodically retrieve the CNF from the NRF repository andstay in sync with 5G systems. The SDN can also mount the NRF repository,NF, and CNF into the configurations database. The SDN can then subscribeto the mounted NFs to receive change notifications of serviceconfigurations. The SDN can also implement a pooling algorithm toretrieve running configurations from the NFs to ensure that the SDN hasa complete view of the service path connections. Furthermore, the SDNcan use the K8 APIs to perform deep discovery of CNF objects thatsupport the system architecture service paths, such as N2, N3, N11, N22,etc. Additionally, the SDN can implement a rule-based service pathconnectivity generator via an SDN graphical user interface (GUI) (e.g.,ODLUX) to create a connection between the NFs. Because the SDN canreceive near-real-time (NRT) logs of containers processing of the callflow, the SDN can relate the CNF objects and their clusters to theservice path model, such as N2, N3, N11, etc. The SDN can also relatethe service path to the log info for a call flow, relate the CNF to thecomputing server, and determine deep vertical cloud fabric connectionsto the network.

A rule-based service path connectivity generator can utilize the SDN GUIto add a connectivity generation feature by which a user can generatetopology reports in an event-based fashion or schedule jobs for batchbased. For example, an event-based topology report can be generated forCNFs deployed in specific core regions. The topology reports cancomprise a predefined format including A side and Z side info (e.g.,nullable & non-nullable types) for each service path (e.g., cNF name,service path type, IP address, virtual local area network (VLAN), PORT)and can show up under a topology report section via the GUI. The valuesin the topology reports can be populated from the configuration database(within the SDN repository). The SDN GUI can comprise a feature todefine rules for topology report generation. Under a rule definitionfeature, there can be a section in which the user can define a name fora report (e.g., based on interface types and/or following a namingconvention) and set targets for the rule definition (A side and Z sideNFs). Under the rule definition feature, there can also be a section inwhich the user can define a set of rules to be applied to the targetNFs. Each rule can have two sides and an operation condition. Each sideof the rule can be a value entered by the user (e.g., VLAN ID, IPaddress, location identifier) or a value from a dropdown list thatcontains objects and attributes from a Yang file of mounted NFs (e.g.,cNF name, IP address, PORT). Additionally, an operation condition can beselected from a dropdown list (e.g., contains, same subnet, equal to, orthe like). Once the topology reports are generated, an action can be setby the user. For example, the action can comprise sending an extensiblemarkup language (XML) file to a consumer landing zone, or publishing ajavascript object notation file in a data movement as a platform(DMaaP). The user can also select the frequency of publishing/sendingthe report.

According to one embodiment, a method can comprise receiving, bysoftware-defined networking equipment comprising a processor, networkrepository function data representative of network functions. Inresponse to receiving the network repository function data, the methodcan comprise storing, by the software-defined networking equipment, thenetwork repository function data in a data store to enable a discoveryfunction associated with the network functions. In response to receivingthe network repository function data, the method can comprise sending,by the software-defined networking equipment to a server, request datarepresentative of a request for a configuration associated with thenetwork functions. Additionally, in response to sending the requestdata, the method can comprise receiving, by the software-definednetworking equipment from the server, notification data representativeof a notification that a configuration of the network repositoryfunction has been modified. Furthermore, in response to receiving thenotification data, the method can comprise determining, by thesoftware-defined networking equipment, a service path associated withthe network functions.

According to another embodiment, a system can facilitate, receivingnetwork repository function data representative of network functions. Inresponse to receiving the network repository function data, the systemcan comprise storing the network repository function data in a datastore to enable a discovery function associated with the networkfunctions. In response to receiving the network repository functiondata, the system can comprise sending request data representative of arequest for a configuration associated with the network functions to aserver. Additionally, in response to sending the request data, thesystem can comprise receiving, from the server, notification datarepresentative of a notification that a configuration of the networkrepository function has been modified. Furthermore, in response toreceiving the notification data, the system can comprise determining aservice path associated with the network functions.

According to yet another embodiment, described herein is amachine-readable medium that can perform the operations comprisingstoring network repository function data, representative of networkfunctions, in a data store to enable a discovery function associatedwith the network functions. In response to storing the networkrepository function data, the machine-readable medium can perform theoperations comprising sending request data, representative of a requestfor a configuration associated with the network functions, to a masterserver. In response to sending the request data, the machine-readablemedium can perform the operations comprising receiving, from the masterserver, notification data representative of a notification that aconfiguration of the network repository function has been modified.Additionally, in response to receiving the notification data, themachine-readable medium can perform the operations comprisingdetermining a service path associated with the network functions.

These and other embodiments or implementations are described in moredetail below with reference to the drawings.

Referring now to FIG. 1, illustrated is an example wirelesscommunication system 100 in accordance with various aspects andembodiments of the subject disclosure. In one or more embodiments,system 100 can include one or more user equipment UEs 102. Thenon-limiting term user equipment can refer to any type of device thatcan communicate with a network node in a cellular or mobilecommunication system.

In various embodiments, system 100 is or includes a wirelesscommunication network serviced by one or more wireless communicationnetwork providers. In example embodiments, a UE 102 can becommunicatively coupled to the wireless communication network via anetwork node 104. The network node (e.g., network node device) cancommunicate with user equipment (UE), thus providing connectivitybetween the UE and the wider cellular network. The UE 102 can sendtransmission type recommendation data to the network node 104. Thetransmission type recommendation data can include a recommendation totransmit data via a closed loop multiple input multiple output (MIMO)mode and/or a rank-1 precoder mode.

A network node can have a cabinet and other protected enclosures, anantenna mast, and multiple antennas for performing various transmissionoperations (e.g., MIMO operations). Network nodes can serve severalcells, also called sectors, depending on the configuration and type ofantenna. In example embodiments, the UE 102 can send and/or receivecommunication data via a wireless link to the network node 104. Thedashed arrow lines from the network node 104 to the UE 102 representdownlink (DL) communications and the solid arrow lines from the UE 102to the network nodes 104 represents an uplink (UL) communication.

System 100 can further include one or more communication serviceprovider networks 106 that facilitate providing wireless communicationservices to various UEs, including UE 102, via the network node 104and/or various additional network devices (not shown) included in theone or more communication service provider networks 106. The one or morecommunication service provider networks 106 can include various types ofdisparate networks, including but not limited to: cellular networks,femto networks, picocell networks, microcell networks, internet protocol(IP) networks Wi-Fi service networks, broadband service network,enterprise networks, cloud based networks, and the like. For example, inat least one implementation, system 100 can be or include a large scalewireless communication network that spans various geographic areas.According to this implementation, the one or more communication serviceprovider networks 106 can be or include the wireless communicationnetwork and/or various additional devices and components of the wirelesscommunication network (e.g., additional network devices and cell,additional UEs, network server devices, etc.). The network node 104 canbe connected to the one or more communication service provider networks106 via one or more backhaul links 108. For example, the one or morebackhaul links 108 can include wired link components, such as a T1/E1phone line, a digital subscriber line (DSL) (e.g., either synchronous orasynchronous), an asymmetric DSL (ADSL), an optical fiber backbone, acoaxial cable, and the like. The one or more backhaul links 108 can alsoinclude wireless link components, such as but not limited to,line-of-sight (LOS) or non-LOS links which can include terrestrialair-interfaces or deep space links (e.g., satellite communication linksfor navigation).

Wireless communication system 100 can employ various cellular systems,technologies, and modulation modes to facilitate wireless radiocommunications between devices (e.g., the UE 102 and the network node104). While example embodiments might be described for 5G new radio (NR)systems, the embodiments can be applicable to any radio accesstechnology (RAT) or multi-RAT system where the UE operates usingmultiple carriers e.g., LTE FDD)/ TDD, GSM/GSM EDGE Radio Access Network(GERAN), CDMA2000 etc.

For example, system 100 can operate in accordance with any 5G, nextgeneration communication technology, or existing communicationtechnologies, various examples of which are listed supra. In thisregard, various features and functionalities of system 100 areapplicable where the devices (e.g., the UEs 102 and the network device104) of system 100 are configured to communicate wireless signals usingone or more multi carrier modulation schemes, wherein data symbols canbe transmitted simultaneously over multiple frequency subcarriers (e.g.,OFDM, CP-OFDM, DFT-spread OFMD, UFMC, FMBC, etc.). The embodiments areapplicable to single carrier as well as to multicarrier (MC) or carrieraggregation (CA) operation of the UE. The term carrier aggregation (CA)is also called (e.g. interchangeably called) “multi-carrier system”,“multi-cell operation”, “multi-carrier operation”, “multi-carrier”transmission and/or reception. Note that some embodiments are alsoapplicable for Multi RAB (radio bearers) on some carriers (that is dataplus speech is simultaneously scheduled).

In various embodiments, system 100 can be configured to provide andemploy 5G wireless networking features and functionalities. 5G wirelesscommunication networks fulfill the demand of exponentially increasingdata traffic and allow people and machines to enjoy gigabit data rateswith virtually zero latency. Compared to 4G, 5G supports more diversetraffic scenarios. For example, in addition to the various types of datacommunication between conventional UEs (e.g., phones, smartphones,tablets, PCs, televisions, Internet enabled televisions, etc.) supportedby 4G networks, 5G networks can be employed to support datacommunication between smart cars in association with driverless carenvironments, as well as machine type communications (MTCs). Consideringthe drastic different communication demands of these different trafficscenarios, the ability to dynamically configure waveform parametersbased on traffic scenarios while retaining the benefits of multi carriermodulation schemes (e.g., OFDM and related schemes) can provide asignificant contribution to the high speed/capacity and low latencydemands of 5G networks. With waveforms that split the bandwidth intoseveral sub-bands, different types of services can be accommodated indifferent sub-bands with the most suitable waveform and numerology,leading to an improved spectrum utilization for 5G networks.

To meet the demand for data centric applications, features of proposed5G networks may include: increased peak bit rate (e.g., 20 Gbps), largerdata volume per unit area (e.g., high system spectral efficiency—forexample about 3.5 times that of spectral efficiency of long termevolution (LTE) systems), high capacity that allows more deviceconnectivity both concurrently and instantaneously, lower battery/powerconsumption (which reduces energy and consumption costs), betterconnectivity regardless of the geographic region in which a user islocated, a larger numbers of devices, lower infrastructural developmentcosts, and higher reliability of the communications.

The 5G access network may utilize higher frequencies (e.g., >6 GHz) toaid in increasing capacity. Currently, much of the millimeter wave(mmWave) spectrum, the band of spectrum between 30 gigahertz (GHz) and300 GHz is underutilized. The millimeter waves have shorter wavelengthsthat range from 10 millimeters to 1 millimeter, and these mmWave signalsexperience severe path loss, penetration loss, and fading. However, theshorter wavelength at mmWave frequencies also allows more antennas to bepacked in the same physical dimension, which allows for large-scalespatial multiplexing and highly directional beamforming.

Performance can be improved if both the transmitter and the receiver areequipped with multiple antennas. Multi-antenna techniques cansignificantly increase the data rates and reliability of a wirelesscommunication system. The use of MIMO techniques, which was introducedin the third-generation partnership project (3GPP) and has been in use(including with LTE), is a multi-antenna technique that can improve thespectral efficiency of transmissions, thereby significantly boosting theoverall data carrying capacity of wireless systems. The use of MIMOtechniques can improve mmWave communications, and has been widelyrecognized a potentially important component for access networksoperating in higher frequencies. MIMO can be used for achievingdiversity gain, spatial multiplexing gain and beamforming gain. Forthese reasons, MIMO systems are an important part of the 3rd and 4thgeneration wireless systems, and are in use in 5G systems.

Referring now to FIG. 2, illustrated is an example schematic systemblock diagram of a master node according to one or more embodiments.

In the embodiment shown in FIG. 2, a master node 200 can comprisesub-components (e.g., ETCD component 202, API server 204, scheduler 206,and controller manager 208), processor 210 and memory 212 canbi-directionally communicate with each other. It should also be notedthat in alternative embodiments that other components including, but notlimited to the sub-components, processor 210, and/or memory 212, can beexternal to the master node 200. Aspects of the processor 210 canconstitute machine-executable component(s) embodied within machine(s),e.g., embodied in one or more computer readable mediums (or media)associated with one or more machines. Such component(s), when executedby the one or more machines, e.g., computer(s), computing device(s),virtual machine(s), etc. can cause the machine(s) to perform theoperations described by the master node 200. In an aspect, the masternode 200 can also include memory 212 that stores computer executablecomponents and instructions.

Referring now to FIG. 3, illustrated is an example schematic systemblock diagram of a containerized network function architecture accordingto one or more embodiments.

Kubernetes can facilitate communication to a master node 200 that cancomprise an API server, a database, a scheduler function, and acontroller manager function. For every NF, there can be a set of workernodes comprising a cAMF 204, a cSMF 206, and/or a cUPF 208. The workernodes make up a cluster and can comprise kubelets, a runtime container,and a kubeproxy. The kubeproxy are APIs for a service path connection.The N2 network service path can flow from a base station equipment(e.g., network node 104) to a DU and CU and then on to the kubeproxy ofthe cAMF 204 via a control plane connection. Then, a userplaneconnection can send this data to the cSMF 206 and the cUPF 208. Forexample, the UE 102 can request a service via the N2 control planeconnection and then the cAMF 204 can identify the cSMF 206 and selectthe cUPF 208 to establish the session via an N3 service path, which canallow the traffic to flow to the internet via an N6 service path. Thekubeproxys are non-transient objects (e.g., static) while the containerruntimes are transient objections (e.g., can change anytime). Therefore,the topological visualization can be built with a non-transient objectthat can be supported by the kubeproxys within the clusters.

Referring now to FIG. 4, illustrated is an example schematic systemblock diagram of a deep service path discovery architecture according toone or more embodiments.

An NRF API (between the NRF 402 and an SDN 404) can be utilized by theSDN 404 to gain information on the NRs because the containers associatedwith the NFs are supposed to register with the NRF 402. In order to knowwhich NFs are in the core network, the NRF 402 can be accessed toprovide a view of which services are supported by the NRF 402. Anenter-discovery of the network services of the service configuration canbe gleaned from the kubernetes cluster as a part of the containerinformation. An integrated operations, or ‘ops’, portal can comprise anoperations and systems support (OSS) module that provides OSSapplications (e.g., Canopi, Geolink, etc.) that can be used to determineservice paths that support the network call flow by discovering theworker nodes and network functions via the NRF 402. However, this willnot provide all of the information. Although the NRF 402 knows the cAMF304, the cSMF 306, and the cUPF308, information regarding a service andnon-service based interfaces may not be known by the NRF 402. The SDN404 can also perform data collection and processing. For example, theSDN 404 can register for notifications (from the NRF 402) to receive anychanges associated with the containerized NF. When a container is spunup by kubernetics, the container can register with the NRF 402.Consequently, when the NRF 402 receives the registration request fromthe SDN 404, the NRF 402 can send a notification, on the NRF API, whichthe SDR 404 can receive and determine that there is now a new NF or thatan NF has been modified. The SDN 404 can perform any additionaloperations to collect additional information on that NF, and then senddown the service configurations (via the cAMF 304) to determine callpaths that are suitable for the UE 102.

Referring now to FIG. 5, illustrated is an example schematic systemblock diagram illustrating facilitation of deep service path discoveryfor cloud native functions in accordance with one or more embodiments ofthe invention.

Alternatively, to receive non-transient data associated with the workernodes, the SDN 404 can communicate with the master node 200. Because themaster node 200 controls the worker nodes via the API server 204, themaster node 200 knows which worker nodes and/or objects are performingprocessing. The scheduler 206 can set policies. For example, if a workernode is not receiving any activity and/or reduced activity for a definedperiod of time set by the scheduler 206, the scheduler 206 can schedulethe activity of the master node 200 to perform status checks on theworker nodes.

Referring now to FIG. 6, illustrated is an example flow diagram for amethod for facilitating deep service path discovery for cloud nativefunctions in accordance with one or more embodiments.

At element 600, the method can comprise receiving, by software-definednetworking equipment comprising a processor, network repository functiondata representative of network functions. At element 602, in response toreceiving the network repository function data, the method can comprisestoring, by the software-defined networking equipment, the networkrepository function data in a data store to enable a discovery functionassociated with the network functions. In response to receiving thenetwork repository function data, at element 604, the method cancomprise sending, by the software-defined networking equipment to aserver, request data representative of a request for a configurationassociated with the network functions. Additionally, at element 606, inresponse to sending the request data, the method can comprise receiving,by the software-defined networking equipment from the server,notification data representative of a notification that a configurationof the network repository function has been modified. Furthermore, atelement 608, in response to receiving the notification data, the methodcan comprise determining, by the software-defined networking equipment,a service path associated with the network functions.

Referring now to FIG. 7, illustrated is an example flow diagram for asystem for facilitation of deep service path discovery for cloud nativefunctions in accordance with one or more embodiments.

At element 700, the system can facilitate receiving network repositoryfunction data representative of network functions. In response toreceiving the network repository function data, at element 702, thesystem can comprise storing the network repository function data in adata store to enable a discovery function associated with the networkfunctions. In response to receiving the network repository functiondata, at element 704, the system can comprise sending request datarepresentative of a request for a configuration associated with thenetwork functions to a server. Additionally, at element 706, in responseto sending the request data, the system can comprise receiving, from theserver, notification data representative of a notification that aconfiguration of the network repository function has been modified.Furthermore, in response to receiving the notification data, at element708, the system can comprise determining a service path associated withthe network functions.

Referring now to FIG. 8, illustrated is an example flow diagram for amachine-readable medium for storage of instructions that, when executed,facilitate deep service path discovery for cloud native functions inaccordance with one or more embodiments.

As illustrated, a non-transitory machine-readable medium can compriseexecutable instructions that, when executed by a processor, facilitateperformance of operations. The operations comprise, at element 800,storing network repository function data, representative of networkfunctions, in a data store to enable a discovery function associatedwith the network functions. At element 802, in response to storing thenetwork repository function data, the operations comprise sendingrequest data, representative of a request for a configuration associatedwith the network functions, to a master server. In response to sendingthe request data, at element 804, the operations comprise receiving,from the master server, notification data representative of anotification that a configuration of the network repository function hasbeen modified. Additionally, at element 806, in response to receivingthe notification data, the operations comprise determining a servicepath associated with the network functions.

Referring now to FIG. 9, illustrated is a schematic block diagram of anexemplary end-user device, such as a mobile handset 900, capable ofconnecting to a network in accordance with some embodiments describedherein. Although a mobile handset 900 is illustrated herein, it will beunderstood that other mobile devices are contemplated herein and thatthe mobile handset 900 is merely illustrated to provide context for theembodiments of the various embodiments described herein. The followingdiscussion is intended to provide a brief, general description of anexample of a suitable environment, such as mobile handset 900, in whichthe various embodiments can be implemented. While the descriptionincludes a general context of computer-executable instructions embodiedon a machine-readable medium, those skilled in the art will recognizethat the innovation also can be implemented in combination with otherprogram modules and/or as a combination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can include computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM,digital video disk (DVD) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, radio frequency (RF), infrared and other wireless media.Combinations of the any of the above should also be included within thescope of computer-readable media.

The mobile handset 900 includes a processor 902 for controlling andprocessing all onboard operations and functions. A memory 904 interfacesto the processor 902 for storage of data and one or more applications906 (e.g., a video player software, user feedback component software,etc.). Other applications can include voice recognition of predeterminedvoice commands that facilitate initiation of the user feedback signals.The applications 906 can be stored in the memory 904 and/or in afirmware 908, and executed by the processor 902 from either or both thememory 904 or/and the firmware 908. The firmware 908 can also storestartup code for execution in initializing the handset 900. Acommunications component 910 interfaces to the processor 902 tofacilitate wired/wireless communication with external systems, e.g.,cellular networks, voice over internet protocol (VoIP) networks, and soon. Here, the communications component 910 can also include a suitablecellular transceiver 911 (e.g., a GSM transceiver) and/or an unlicensedtransceiver 913 (e.g., Wi-Fi, WiMax) for corresponding signalcommunications. The handset 900 can be a device such as a cellulartelephone, a PDA with mobile communications capabilities, andmessaging-centric devices. The communications component 910 alsofacilitates communications reception from terrestrial radio networks(e.g., broadcast), digital satellite radio networks, and Internet-basedradio services networks.

The mobile handset 900 includes a display 912 for displaying text,images, video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 912 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 912 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface914 is provided in communication with the processor 902 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE1394) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the handset 900, for example. Audio capabilities areprovided with an audio I/O component 916, which can include a speakerfor the output of audio signals related to, for example, indication thatthe user pressed the proper key or key combination to initiate the userfeedback signal. The audio I/O component 916 also facilitates the inputof audio signals through a microphone to record data and/or telephonyvoice data, and for inputting voice signals for telephone conversations.

The handset 900 can include a slot interface 918 for accommodating a SIC(Subscriber Identity Component) in the form factor of a card SubscriberIdentity Module (SIM) or universal SIM 920, and interfacing the SIM card920 with the processor 902. However, it is to be appreciated that theSIM card 920 can be manufactured into the handset 900, and updated bydownloading data and software.

The handset 900 can process IP data traffic through the communicationcomponent 910 to accommodate IP traffic from an IP network such as, forexample, the Internet, a corporate intranet, a home network, a personarea network, etc., through an ISP or broadband cable provider. Thus,VoIP traffic can be utilized by the handset 900 and IP-based multimediacontent can be received in either an encoded or decoded format.

A video processing component 922 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 922can aid in facilitating the generation, editing and sharing of videoquotes. The handset 900 also includes a power source 924 in the form ofbatteries and/or an alternating current (AC) power subsystem, whichpower source 924 can interface to an external power system or chargingequipment (not shown) by a power 110 component 926.

The handset 900 can also include a video component 930 for processingvideo content received and, for recording and transmitting videocontent. For example, the video component 930 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 932 facilitates geographically locating the handset 900. Asdescribed hereinabove, this can occur when the user initiates thefeedback signal automatically or manually. A user input component 934facilitates the user initiating the quality feedback signal. The userinput component 934 can also facilitate the generation, editing andsharing of video quotes. The user input component 934 can include suchconventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 906, a hysteresis component 936facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with the access point. Asoftware trigger component 938 can be provided that facilitatestriggering of the hysteresis component 938 when the Wi-Fi transceiver913 detects the beacon of the access point. A SIP client 940 enables thehandset 900 to support SIP protocols and register the subscriber withthe SIP registrar server. The applications 906 can also include a client942 that provides at least the capability of discovery, play and storeof multimedia content, for example, music.

The mobile handset 900, as indicated above related to the communicationscomponent 910, includes an indoor network radio transceiver 913 (e.g.,Wi-Fi transceiver). This function supports the indoor radio link, suchas IEEE 802.11, for the mobile handset 900, e.g., a dual-mode GSMhandset. The mobile handset 900 can accommodate at least satellite radioservices through a handset that can combine wireless voice and digitalradio chipsets into a single handheld device.

In order to provide additional context for various embodiments describedherein, FIG. 10 and the following discussion are intended to provide abrief, general description of a suitable computing environment 1000 inwhich the various embodiments of the embodiment described herein can beimplemented. While the embodiments have been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that theembodiments can be also implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the disclosed methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, IoT devices, distributedcomputing systems, as well as personal computers, hand-held computingdevices, microprocessor-based or programmable consumer electronics, andthe like, each of which can be operatively coupled to one or moreassociated devices.

The illustrated embodiments of the embodiments herein can be alsopracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable media, machine-readable media, and/orcommunications media, which two terms are used herein differently fromone another as follows. Computer-readable media or machine-readablemedia can be any available media that can be accessed by the computerand includes both volatile and nonvolatile media, removable andnon-removable media. By way of example, and not limitation,computer-readable media or machine-readable media can be implemented inconnection with any method or technology for storage of information suchas computer-readable or machine-readable instructions, program modules,structured data or unstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), smart card, flashmemory (e.g., card, stick, key drive) or other memory technology,compact disk (CD), compact disk read only memory (CD-ROM), digitalversatile disk (DVD), Blu-ray™ disc (BD) or other optical disk storage,floppy disk storage, hard disk storage, magnetic cassettes, magneticstrip(s), magnetic tape, magnetic disk storage or other magnetic storagedevices, solid state drives or other solid state storage devices, avirtual device that emulates a storage device (e.g., any storage devicelisted herein), or other tangible and/or non-transitory media which canbe used to store desired information. In this regard, the terms“tangible” or “non-transitory” herein as applied to storage, memory orcomputer-readable media, are to be understood to exclude onlypropagating transitory signals per se as modifiers and do not relinquishrights to all standard storage, memory or computer-readable media thatare not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 10, the example environment 1000 forimplementing various embodiments of the aspects described hereinincludes a computer 1002, the computer 1002 including a processing unit1004, a system memory 1006 and a system bus 1008. The system bus 1008couples system components including, but not limited to, the systemmemory 1006 to the processing unit 1004. The processing unit 1004 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures can also be employed as theprocessing unit 1004.

The system bus 1008 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1006includes ROM 1010 and RAM 1012. A basic input/output system (BIOS) canbe stored in a non-volatile memory such as ROM, erasable programmableread only memory (EPROM), EEPROM, which BIOS contains the basic routinesthat help to transfer information between elements within the computer1002, such as during startup. The RAM 1012 can also include a high-speedRAM such as static RAM for caching data.

The computer 1002 further includes an internal hard disk drive (HDD)1014 (e.g., EIDE, SATA), one or more external storage devices 1016(e.g., a magnetic floppy disk drive 1016, a memory stick or flash drivereader, a memory card reader, etc.) and an optical disk drive 1020(e.g., which can read or write from a CD-ROM disc, a DVD, a BD, etc.).While the internal HDD 1014 is illustrated as located within thecomputer 1002, the internal HDD 1014 can also be configured for externaluse in a suitable chassis (not shown). Additionally, while not shown inenvironment 1000, a solid state drive (SSD) could be used in additionto, or in place of, an HDD 1014. The HDD 1014, external storagedevice(s) 1016 and optical disk drive 1020 can be connected to thesystem bus 1008 by an HDD interface 1024, an external storage interface1026 and an optical drive interface 1028, respectively. The interface1024 for external drive implementations can include at least one or bothof USB and IEEE 1394 interface technologies. Other external driveconnection technologies are within contemplation of the embodimentsdescribed herein.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1002, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to respective types of storage devices, it should beappreciated by those skilled in the art that other types of storagemedia which are readable by a computer, whether presently existing ordeveloped in the future, could also be used in the example operatingenvironment, and further, that any such storage media can containcomputer-executable instructions for performing the methods describedherein.

A number of program modules can be stored in the drives and RAM 1012,including an operating system 1030, one or more application programs1032, other program modules 1034 and program data 1036. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1012. The systems and methods described herein can beimplemented utilizing various commercially available operating systemsor combinations of operating systems.

Computer 1002 can optionally include emulation technologies. Forexample, a hypervisor (not shown) or other intermediary can emulate ahardware environment for operating system 1030, and the emulatedhardware can optionally be different from the hardware illustrated inFIG. 10. In such an embodiment, operating system 1030 can include onevirtual machine (VM) of multiple VMs hosted at computer 1002.Furthermore, operating system 1030 can provide runtime environments,such as the Java runtime environment or the .NET framework, forapplications 1032. Runtime environments are consistent executionenvironments that allow applications 1032 to run on any operating systemthat includes the runtime environment. Similarly, operating system 1030can support containers, and applications 1032 can be in the form ofcontainers, which are lightweight, standalone, executable packages ofsoftware that include, e.g., code, runtime, system tools, systemlibraries and settings for an application.

Further, computer 1002 can be enable with a security module, such as atrusted processing module (TPM). For instance with a TPM, bootcomponents hash next in time boot components, and wait for a match ofresults to secured values, before loading a next boot component. Thisprocess can take place at any layer in the code execution stack ofcomputer 1002, e.g., applied at the application execution level or atthe operating system (OS) kernel level, thereby enabling security at anylevel of code execution.

A user can enter commands and information into the computer 1002 throughone or more wired/wireless input devices, e.g., a keyboard 1038, a touchscreen 1040, and a pointing device, such as a mouse 1042. Other inputdevices (not shown) can include a microphone, an infrared (IR) remotecontrol, an RF remote control, or other remote control, a joystick, avirtual reality controller and/or virtual reality headset, a game pad, astylus pen, an image input device, e.g., camera(s), a gesture sensorinput device, a vision movement sensor input device, an emotion orfacial detection device, a biometric input device, e.g., fingerprint oriris scanner, or the like. These and other input devices are oftenconnected to the processing unit 1004 through an input device interface1044 that can be coupled to the system bus 1008, but can be connected byother interfaces, such as a parallel port, an IEEE 1394 serial port, agame port, a USB port, an IR interface, a BLUETOOTH® interface, etc.

A monitor 1046 or other type of display device can be also connected tothe system bus 1008 via an interface, such as a video adapter 1048. Inaddition to the monitor 1046, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1002 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1050. The remotecomputer(s) 1050 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1002, although, for purposes of brevity, only a memory/storage device1052 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1054 and/orlarger networks, e.g., a wide area network (WAN) 1056. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1002 can beconnected to the local network 1054 through a wired and/or wirelesscommunication network interface or adapter 1058. The adapter 1058 canfacilitate wired or wireless communication to the LAN 1054, which canalso include a wireless access point (AP) disposed thereon forcommunicating with the adapter 1058 in a wireless mode.

When used in a WAN networking environment, the computer 1002 can includea modem 1060 or can be connected to a communications server on the WAN1056 via other means for establishing communications over the WAN 1056,such as by way of the Internet. The modem 1060, which can be internal orexternal and a wired or wireless device, can be connected to the systembus 1008 via the input device interface 1044. In a networkedenvironment, program modules depicted relative to the computer 1002 orportions thereof, can be stored in the remote memory/storage device1052. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

When used in either a LAN or WAN networking environment, the computer1002 can access cloud storage systems or other network-based storagesystems in addition to, or in place of, external storage devices 1016 asdescribed above. Generally, a connection between the computer 1002 and acloud storage system can be established over a LAN 1054 or WAN 1056e.g., by the adapter 1058 or modem 1060, respectively. Upon connectingthe computer 1002 to an associated cloud storage system, the externalstorage interface 1026 can, with the aid of the adapter 1058 and/ormodem 1060, manage storage provided by the cloud storage system as itwould other types of external storage. For instance, the externalstorage interface 1026 can be configured to provide access to cloudstorage sources as if those sources were physically connected to thecomputer 1002.

The computer 1002 can be operable to communicate with any wirelessdevices or entities operatively disposed in wireless communication,e.g., a printer, scanner, desktop and/or portable computer, portabledata assistant, communications satellite, any piece of equipment orlocation associated with a wirelessly detectable tag (e.g., a kiosk,news stand, store shelf, etc.), and telephone. This can include Wi-Fiand BLUETOOTH® wireless technologies. Thus, the communication can be apredefined structure as with a conventional network or simply an ad hoccommunication between at least two devices.

The computer is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and BluetoothTMwireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi allows connection to the Internet from a couch at home, a bed in ahotel room, or a conference room at work, without wires. Wi-Fi is awireless technology similar to that used in a cell phone that enablessuch devices, e.g., computers, to send and receive data indoors and out;anywhere within the range of a base station. Wi-Fi networks use radiotechnologies called IEEE 802.11 (a, b, g, etc.) to provide secure,reliable, fast wireless connectivity. A Wi-Fi network can be used toconnect computers to each other, to the Internet, and to wired networks(which use IEEE 802.3 or Ethernet). Wi-Fi networks operate in theunlicensed 2.4 and 5 GHz radio bands, at an 11 Mbps (802.11a) or 54 Mbps(802.11b) data rate, for example, or with products that contain bothbands (dual band), so the networks can provide real-world performancesimilar to the basic 10BaseT wired Ethernet networks used in manyoffices.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the subject matter has been described herein inconnection with various embodiments and corresponding FIGs, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

What is claimed is:
 1. A method, comprising: receiving, bysoftware-defined networking equipment comprising a processor, networkrepository function data representative of network functions; inresponse to receiving the network repository function data, storing, bythe software-defined networking equipment, the network repositoryfunction data in a data store to enable a discovery function associatedwith the network functions; in response to receiving the networkrepository function data, sending, by the software-defined networkingequipment to a server, request data representative of a request for aconfiguration associated with the network functions; in response tosending the request data, receiving, by the software-defined networkingequipment from the server, notification data representative of anotification that a configuration of the network repository function hasbeen modified; and in response to receiving the notification data,determining, by the software-defined networking equipment, a servicepath associated with the network functions.
 2. The method of claim 1,wherein the network functions comprise a userplane function associatedwith a worker node device.
 3. The method of claim 2, wherein the serveris a master node device that oversees the worker node device.
 4. Themethod of claim 1, wherein the software-defined networking equipmentcommunicates with the server via an application program interface. 5.The method of claim 1, further comprising: facilitating, by thesoftware-defined networking equipment, access to the service path via auser equipment.
 6. The method of claim 1, wherein the network functionscomprise an access and mobility management function.
 7. The method ofclaim 1, wherein the network functions comprise a session managementfunction.
 8. Software-defined networking equipment, comprising: aprocessor; and a memory that stores executable instructions that, whenexecuted by the processor, facilitate performance of operations,comprising: receiving network repository function data representative ofnetwork functions; in response to receiving the network repositoryfunction data, storing the network repository function data in a datastore to enable a discovery function associated with the networkfunctions; in response to receiving the network repository functiondata, sending request data representative of a request for aconfiguration associated with the network functions to a server; inresponse to sending the request data, receiving, from the server,notification data representative of a notification that a configurationof the network repository function has been modified; and in response toreceiving the notification data, determining a service path associatedwith the network functions.
 9. The software-defined networking equipmentof claim 8, wherein sending the request data comprises registering withthe server for updates associated with the network functions.
 10. Thesoftware-defined networking equipment of claim 8, wherein the operationsfurther comprise: receiving, from network repository function nodeequipment, an indication that a network function has been added to thenetwork functions.
 11. The software-defined networking equipment ofclaim 10, wherein the network function is a session management networkfunction.
 12. The software-defined networking equipment of claim 11,wherein the operations further comprise: in response to determining theservice path, sending service configuration data to the sessionmanagement network function to facilitate network access via a userequipment.
 13. The software-defined networking equipment of claim 10,wherein the network function is an access and mobility managementfunction.
 14. The software-defined networking equipment of claim 13,wherein the operations further comprise: in response to determining theservice path, sending service configuration data to the access andmobility management function to facilitate network access via a userequipment.
 15. A non-transitory machine-readable medium, comprisingexecutable instructions that, when executed by a processor, facilitateperformance of operations, comprising: storing network repositoryfunction data, representative of network functions, in a data store toenable a discovery function associated with the network functions; inresponse to storing the network repository function data, sendingrequest data, representative of a request for a configuration associatedwith the network functions, to a master server; in response to sendingthe request data, receiving, from the master server, notification datarepresentative of a notification that a configuration of the networkrepository function has been modified; and in response to receiving thenotification data, determining a service path associated with thenetwork functions.
 16. The non-transitory machine-readable medium ofclaim 15, wherein the operations further comprise: retrievingconfiguration data, representative of a running configuration, from anetwork server hosting a network function of the network functions. 17.The non-transitory machine-readable medium of claim 16, wherein thenetwork function is a userplane function.
 18. The non-transitorymachine-readable medium of claim 15, wherein the operations furthercomprise: in response to determining the service path, executing a callvia the service path for a mobile device.
 19. The non-transitorymachine-readable medium of claim 18, wherein the operations furthercomprise: in response to executing the call via the service path,generating a topology report for the network functions.
 20. Thenon-transitory machine-readable medium of claim 19, wherein theoperations further comprise: in response to generating the topologyreport, sending the topology report for display via a graphical userinterface.